If I make uncaught exceptions in browser-chrome mochitests cause test failures, browser_tabview_bug627288.js fails as follows: TEST-START | chrome://mochitests/content/browser/browser/base/content/test/tabview/browser_tabview_bug627288.js before 565248, after 532480, break 0988a000 before 565248, after 524288, break 0988a000 TEST-PASS | chrome://mochitests/content/browser/browser/base/content/test/tabview/browser_tabview_bug627288.js | tabItem shows cached data before 532480, after 520192, break 0988a000 TEST-PASS | chrome://mochitests/content/browser/browser/base/content/test/tabview/browser_tabview_bug627288.js | tab label is up-to-date before 565248, after 532480, break 0988a000 TEST-PASS | chrome://mochitests/content/browser/browser/base/content/test/tabview/browser_tabview_bug627288.js | tabItem does not show cached data NEXT ERROR TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/base/content/test/tabview/browser_tabview_bug627288.js | [SimpleTest/SimpleTest.js, window.onerror] - An error occurred: self.tab is null at chrome://browser/content/tabview.js:5091 TEST-INFO | chrome://mochitests/content/browser/browser/base/content/test/tabview/browser_tabview_bug627288.js | Console message: [JavaScript Error: "self.tab is null" {file: "chrome://browser/content/tabview.js" line: 5091}] INFO TEST-END | chrome://mochitests/content/browser/browser/base/content/test/tabview/browser_tabview_bug627288.js | finished in 1057ms

Please double-check on mozilla-central tip -- this should be fixed by bug 664670.

Indeed it is, thanks.